Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1033

reference: 221-tree-1
name: 1033
tree-preservation-order: undefined
221-tpo-1
uprn
address-text
point: POINT (-0.937909 50.859142)
geometry: MULTIPOLYGON (((-0.937881 50.859139,-0.937882 50.859145,-0.937886 50.859150,-0.937892 50.859154,-0.937909 50.859157,-0.937926 50.859154,-0.937932 50.859150,-0.937938 50.859140,-0.937933 50.859129,-0.937918 50.859122,-0.937910 50.859121,-0.937901 50.859122,-0.937893 50.859125,-0.937882 50.859134,-0.937881 50.859139)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL